Dynomotion

Group: DynoMotion Message: 4608 From: himykabibble Date: 4/22/2012
Subject: v429 Question
I've tried twice to post a question, and Yahoo, in it's infinite wisdom, has chosen to disappear both...

I see in the v429 release notes that the structure of the Controller/Interpreter/Coordmotion has changed. Is it different from v429z? Will I need to make code changes in my app, or should I be able to just install v429 and do a new build?

Regards,
Ray L.
Group: DynoMotion Message: 4609 From: brad murry Date: 4/22/2012
Subject: Re: v429 Question
There are no major changes from 429z to 429, just some bug fixes.

You have already worked through the architecture update.

-Brad Murry

From: himykabibble
Sent: 4/22/2012 8:05 AM
To: DynoMotion@yahoogroups.com
Subject: [DynoMotion] v429 Question

 

I've tried twice to post a question, and Yahoo, in it's infinite wisdom, has chosen to disappear both...

I see in the v429 release notes that the structure of the Controller/Interpreter/Coordmotion has changed. Is it different from v429z? Will I need to make code changes in my app, or should I be able to just install v429 and do a new build?

Regards,
Ray L.

Group: DynoMotion Message: 4610 From: Tom Kerekes Date: 4/22/2012
Subject: Re: v429 Question
Hi Ray,
 
I think the only change to the interface was expanding those origin offsets to 6 axes that you asked for.
 
Regards
TK

Group: DynoMotion Message: 4613 From: himykabibble Date: 4/22/2012
Subject: Re: v429 Question
Tom,

Cool! Thanks!

I know you and Brad have probably missed me bugging you lately, but everything has been working absolutely *flawlessly* for some time now! Not one, single, solitary hiccup in all this time! After those last few months with Mach3, this is SUCH a relief! There were one or two times I *thought* it had done something unexpected, but in every case it turned out to be either a G-code problem, or operator error. :-) It was a lot of work getting to this point, but now that it's all working, it was worth every bit of it. I can finally TRUST my machine again, and don't feel I have to sit there and watch it every minute with a finger always hovering over the E-Stop!

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> I think the only change to the interface was expanding those origin offsets to 6 axes that you asked for.
>  
> Regards
> TK
>
> From: brad murry <bradodarb@...>
> To: "DynoMotion@yahoogroups.com" <DynoMotion@yahoogroups.com>
> Sent: Sunday, April 22, 2012 9:15 AM
> Subject: RE: [DynoMotion] v429 Question
>
>
>  
> There are no major changes from 429z to 429, just some bug fixes.
>
> You have already worked through the architecture update.
>
> -Brad Murry
> From: himykabibble
> Sent: 4/22/2012 8:05 AM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] v429 Question
>
>
>  
> I've tried twice to post a question, and Yahoo, in it's infinite wisdom, has chosen to disappear both...
>
> I see in the v429 release notes that the structure of the Controller/Interpreter/Coordmotion has changed. Is it different from v429z? Will I need to make code changes in my app, or should I be able to just install v429 and do a new build?
>
> Regards,
> Ray L.
>
Group: DynoMotion Message: 4615 From: Tom Kerekes Date: 4/22/2012
Subject: Re: v429 Question
Thanks for taking time for the positive feedback Ray.  Coming from you that says a lot :}
 
Regards
TK

Group: DynoMotion Message: 4617 From: tmday7 Date: 4/22/2012
Subject: Re: v429 Question
Thats good to here Ray:)

Tom, updated to 429 with no problems including the Mach plugin.
Thanks,
Troy

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Tom,
>
> Cool! Thanks!
>
> I know you and Brad have probably missed me bugging you lately, but everything has been working absolutely *flawlessly* for some time now! Not one, single, solitary hiccup in all this time! After those last few months with Mach3, this is SUCH a relief! There were one or two times I *thought* it had done something unexpected, but in every case it turned out to be either a G-code problem, or operator error. :-) It was a lot of work getting to this point, but now that it's all working, it was worth every bit of it. I can finally TRUST my machine again, and don't feel I have to sit there and watch it every minute with a finger always hovering over the E-Stop!
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > I think the only change to the interface was expanding those origin offsets to 6 axes that you asked for.
> >  
> > Regards
> > TK
> >
> > From: brad murry <bradodarb@>
> > To: "DynoMotion@yahoogroups.com" <DynoMotion@yahoogroups.com>
> > Sent: Sunday, April 22, 2012 9:15 AM
> > Subject: RE: [DynoMotion] v429 Question
> >
> >
> >  
> > There are no major changes from 429z to 429, just some bug fixes.
> >
> > You have already worked through the architecture update.
> >
> > -Brad Murry
> > From: himykabibble
> > Sent: 4/22/2012 8:05 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] v429 Question
> >
> >
> >  
> > I've tried twice to post a question, and Yahoo, in it's infinite wisdom, has chosen to disappear both...
> >
> > I see in the v429 release notes that the structure of the Controller/Interpreter/Coordmotion has changed. Is it different from v429z? Will I need to make code changes in my app, or should I be able to just install v429 and do a new build?
> >
> > Regards,
> > Ray L.
> >
>